Release 1.12.0 - #45

Bumps the version to 1.12.0 and dates the changelog. It also moves the version in action.yml and the README's CI snippets to the new release.

Ships #44: a column placed after another keeps its time shape, nothing piles up on --as-of midnight, and the determinism promise is now per version.

After merging, publishing the GitHub release triggers the PyPI upload.

Release notes (draft)

A column placed after another now keeps its time shape, and no longer piles rows up on --as-of midnight. Both fixes change what some models generate for the same seed: see Upgrading below.

Fixed

• A column placed after another keeps its time shape. A date or timestamp column with an
  after, or one a created/updated/closed name pair places after another, was set to that
  column plus a random gap, which threw away the draw its business_hours had shaped:
  appointments after a booking with business_hours: true came out at 3am as often as at
  10am. The gap still decides roughly when; business_hours (the column's own, or the run's)
  now decides the weekday and hour. The share of such a column in weekday working hours goes
  from about 29%, the rate of a uniform draw, to about 72%, the same as a column drawn on its
  own. The column's growth and seasonality still come from the column it follows.
• No pile-up at --as-of midnight. A gap that ran past the end of the window set the value
  to exactly --as-of midnight, so about 1% of a dependent column's rows shared that one
  timestamp. Such a gap is now drawn again, and after 20 tries the value is drawn evenly
  between the column it follows and the window's end. A when column filled in on day 0 is
  placed the same way.

Changed

• The determinism promise is per version. The same model, seed, --as-of and options still
  give the same files, byte for byte, on any machine and any day, with the same model2data
  version. A new release may change what a seed produces, and when it does the changelog says
  which models are affected and why. (The README promised the same bytes across every 1.x
  release.)

Upgrading

Output changes for the same seed in a table with a column placed after another, wherever either
fix applies: a dependent column with business hours (its own or the run's), and every table
where a row's gap ran past --as-of (about 1 row in 100, so most such tables beyond a few
hundred rows). Values drawn after the first such row in a table change too. A table with no
column placed after another writes the same bytes as in 1.11.0.

Committed fixtures from 1.11.0 will differ when regenerated. Pin model2data==1.11.0 (or the
Action's version: 1.11.0) to keep them, or regenerate and commit the new ones.

Full changelog: v1.11.0...v1.12.0

🤖 Generated with Claude Code